💡 Codex Review

Return after stop-loss fallback in reversal path

With the new <= check, insufficient-balance cases now enter this branch, call execute_stop_loss(), and then continue into new-bot creation and reversal orders. In this flow, _is_reversal_possible(...) returns current_contracts when reversal is not affordable, so continuing after stop-loss can still submit unintended reversal orders immediately after closing, which contradicts the fallback message and can produce extra trades/fees in live futures accounts.

Use a stable prior point for live PnL comparison

This equality heuristic (abs(lastBenchmarkValue - latestPortfolioValue) < 0.0001) is brittle now that the backend appends a live point per benchmark request: when /balance and /benchmark-series are fetched at slightly different times, small market moves frequently make the values differ by more than the threshold. In that case, previousPortfolioValue falls back to the last benchmark value (another live sample) instead of the prior stored snapshot, so displayed PnL becomes near-zero/noisy rather than reflecting the intended last-snapshot delta.